Using a Content Delivery Network for Security Monitoring

ABSTRACT

A content delivery network includes a plurality of cache servers. Each cache server is configured to receive a request for content from a client system and receive content and security data from a content server. Each cache server is further configured to provide the content to the client system and provide the security data to a monitoring system.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to communications networks, and more particularly relates to using a content delivery network (CDN) for security monitoring.

BACKGROUND

Packet-switched networks, such as networks based on the TCP/IP protocol suite, can distribute a rich array of digital content to a variety of client applications. One popular application is a personal computer browser for retrieving documents over the Internet written in the Hypertext Markup Language (HTML). Frequently, these documents include embedded content. Where once the digital content consisted primarily of text and static images, digital content has grown to include audio and video content as well as dynamic content customized for an individual user.

It is often advantageous when distributing digital content across a packet-switched network to divide the duty of answering content requests among a plurality of geographically dispersed servers. For example, popular Web sites on the Internet often provide links to “mirror” sites that replicate original content at a number of geographically dispersed locations. A more recent alternative to mirroring is content distribution networks (CDNs) that dynamically redirect content requests to a cache server situated closer to the client issuing the request. CDNs either co-locate cache servers within Internet Service Providers or deploy them within their own separate networks.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration, elements illustrated in the Figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements are exaggerated relative to other elements. Embodiments incorporating teachings of the present disclosure are shown and described with respect to the drawings presented herein, in which:

FIG. 1 is a block diagram illustrating a communications network in accordance with one embodiment of the present disclosure;

FIG. 2 is a block diagram illustrating an exemplary system for security monitoring;

FIG. 3 is a flow diagram illustrating an exemplary method of using a CDN for security monitoring; and

FIG. 4 is an illustrative embodiment of a general computer system.

The use of the same reference symbols in different drawings indicates similar or identical items.

DETAILED DESCRIPTION OF THE DRAWINGS

The numerous innovative teachings of the present application will be described with particular reference to the presently preferred exemplary embodiments. However, it should be understood that this class of embodiments provides only a few examples of the many advantageous uses of the innovative teachings herein. In general, statements made in the specification of the present application do not necessarily limit any of the various claimed inventions. Moreover, some statements may apply to some inventive features but not to others.

FIG. 1 shows a geographically dispersed network 100, such as the Internet. Network 100 can include routers 102, 104, and 106 that communicate with each other and form an autonomous system (AS) 108. AS 108 can connect to other ASs that form network 100 through peering points at routers 102 and 104. Additionally, AS 108 can include client systems 110, 112, 114, and 116 connected to respective routers 102, 104, and 106 to access the network 100. Router 102 can provide ingress and egress for client system 110. Similarly, router 104 can provide ingress and egress for client system 112. Router 106 can provide ingress and egress for both of client systems 114 and 116.

AS 108 can further include a Domain Name System (DNS) server 118. DNS server 118 can translate a human readable hostname, such as www.att.com, into an Internet Protocol (IP) address. For example, client system 110 can send a request to resolve a hostname to DNS server 118. DNS server 118 can provide client system 110 with an IP address corresponding to the hostname. DNS server 118 may provide the IP address from a cache of hostname-IP address pairs or may request the IP address corresponding to the hostname from an authoritative DNS server for the domain to which the hostname belongs.

Client systems 110, 112, 114, and 116 can retrieve information from a server 120. For example, client system 112 can retrieve a web page provided by server 120. Additionally, client system 112 may download content files, such as graphics, audio, and video content, and program files such as software updates, from server 120. The time required for client system 112 to retrieve the information from the server 120 normally is related to the size of the file, the distance the information travels, and congestion along the route. Additionally, the load on the server 120 is related to the number of client systems 110, 112, 114, and 116 that are actively retrieving information from the server 120. As such, the resources such as processor, memory, and bandwidth available to the server 120 limit the number of client systems 110, 112, 114, and 116 that can simultaneously retrieve information from the server 120.

Additionally, the network can include cache servers 122 and 124 that replicate content on the server 120 and that can be located more closely within the network to the client systems 110, 112, 114, and 116. Cache server 122 can link to router 102, and cache server 124 can link to router 106. Client systems 110, 112, 114, and 116 can be assigned cache server 122 or 124 to decrease the time needed to retrieve information, such as by selecting the cache server closer to the particular client system. The network distance between a cache server and client system can be determined by network cost and access time. As such, the effective network distance between the cache server and the client system may be different from the geographic distance.

When assigning cache servers 122 and 124 to client systems 110, 112, 114, and 116, the cache server closest to the client can be selected. The closest cache server may be the cache server having a shortest network distance, a lowest network cost, a lowest network latency, a highest link capacity, or any combination thereof. Client system 110 can be assigned cache server 122, and client systems 114 and 116 can be assigned to cache server 124. The network costs of assigning client system 112 to either of cache server 122 or 124 may be substantially identical. When the network costs associated with the link between router 102 and router 104 are marginally lower than the network costs associated with the link between router 104 and router 106, client 112 may be assigned to cache server 124.

Client system 112 may send a request for information to cache server 124. If cache server 124 has the information stored in a cache, it can provide the information to client system 112. This can decrease the distance the information travels and reduce the time to retrieve the information. Alternatively, when cache server 124 does not have the information, it can retrieve the information from server 120 prior to providing the information to the client system 112. In an embodiment, cache server 124 may attempt to retrieve the information from cache server 122 prior to retrieving the information from server 120. The cache server 124 may retrieve the information from the server 120 only once, reducing the load on server 120 and network 100 such as, for example, when client system 114 requests the same information.

Cache server 124 can have a cache of a limited size. The addition of new content to the cache may require old content to be removed from the cache. The cache may utilize a least recently used (LRU) policy, a least frequently used (LFU) policy, or another cache policy known in the art. When the addition of relatively cold or less popular content to the cache causes relatively hot or more popular content to be removed from the cache, an additional request for the relatively hot content can increase the time required to provide the relatively hot content to the client system, such as client system 114. To maximize the cost and time savings of providing content from the cache, the most popular content may be stored in the cache, while less popular content is retrieved from server 120.

FIG. 2 illustrates an exemplary system, generally designated 200, for security monitoring. Content Provider 202 can have content servers 204, 206, and 208 for providing content. In an embodiment, content servers 204, 206, and 208 can be geographically distributed to reduce the likelihood of simultaneous failure. CDN 210 can include cache servers 212, 214, 216, and 218 for providing the content to client systems, such as client system 112. The cache servers 212, 214, 216, and 218 can retrieve content from the content servers 204, 206, and 208 in response to a request from a client system. Alternatively, content servers 204, 206, and 208 can upload content to the cache servers 212, 214, 216, and 218 when new content is created or content is updated. Additionally, the content servers 204, 206, and 208 can provide security data along with any content sent to cache servers 212, 214, 216, and 218.

The security data can be a data file including information from system logs, configuration information, system information, and the like. The configuration information can include the size of configuration files, last modification time of the configuration files, hashes of the configuration files, recent changes to the configuration files, or any combination thereof. System information can include CPU utilization, bandwidth utilization, storage utilization, number of concurrent connections, processor temperature, fan speed, drive status such as Self Monitoring Analysis and Reporting Technology (S.M.A.R.T.) information, other indicators of the current operation of the content server, or any combination thereof.

Monitoring system 220 can retrieve the security data from the cache servers 212, 214, 216, and 218 to identify any changes in the operation of the content servers 204, 206, and 208. These changes can be due to malicious activity, configuration changes, hardware malfunctions, or the like. For example, the monitoring system 220 can compare the security data obtained from different cache servers and comparing the security data to historical trends to identify anomalies that may indicate problems with one of the content servers. Additionally, the monitoring system 220 can monitor changes to configuration files for unauthorized activity. Further, the monitoring system 220 can analyze the log files to identify system errors or malicious attempts at accessing the content server.

In an embodiment, cache server 212 can obtain security data from content server 204. The security data obtained by cache server 212 can include information from a log file containing an entry stating that at time 2:05:09 an event X was observed. Separately, cache server 214 can obtain security data from content server 204. The security data obtained by cache server 214 can include information from a log file containing an alternate entry for time 2:05:09 stating that event Y (different from X) was observed. Alternatively, the security data obtained by cache server 214, while encompassing a period of time including 2:05:09, may not have an entry for time 2:05:09. The monitoring system 220, when comparing the security data obtained from cache servers 212 and 214, can detects the difference as an anomaly and can generate an alert to indicate a potential compromise leading to the event at 2:05:09 being changed or deleted occurred on content server 204 between the time cache server 212 obtained the security data and the time the cache server 214 obtained the security data. In an embodiment, network hardware, such as routers, intrusion detection systems, network attached storage systems, and the like, can send logging information to one of the content servers and the content server can include that information with the security data sent to the cache servers.

FIG. 3 illustrates an exemplary method of using a CDN for security monitoring. At 302, a cache server, such as cache server 212, can request content from a content server, such as content server 204. The request can be in response to the cache server receiving a request for the content from a client system and determining that the content is not cached or is out-of-date. At 304, the content server can provide the cache server with the content and a separate data file containing security data. The security data can include recent log activity, system resource utilization, recent changes to configuration files, or any combination thereof.

In an alternate embodiment, the content server can initiate the transfer of new content, such as when an update is made to a file having a long time-to-live value or when a software update for client systems is released. The content server can send security data at substantially the same time as sending the new content. Generally, the security data can be transferred to the cache server whenever the content server sends content to the cache server.

At 306, the monitoring service, such as monitoring service 220, can retrieve the security data from the cache server. The monitoring service can periodically poll the cache server to determine if new security data is available from the cache server. Additionally, the monitoring service can retrieve security data from multiple cache servers.

At 308, the monitoring service can analyze the security data. For example, the monitoring service can compare the security data of a similar time period retrieved from different cache servers. A difference in security data covering a similar time period, such as recent log activity, could indicate an attacker was able to gain access to the content server and altered the logs in an attempt to avoid detection. In another example, the monitoring service could compare system resource utilization to historical patterns of system resource utilization. A significant change in the system resource utilization could indicate an ongoing denial-of-service attack or an attacker scanning for vulnerabilities. Alternatively, abnormal system resource utilization may indicate a configuration or hardware problem that should be addressed before it causes a system failure.

At 310, the monitoring service can determine if an anomaly is detected. When an anomaly is detected, the monitoring service can send an alert such as to a system administrator or network security specialist, as shown at 312. The anomaly can include altered logs files, modified configuration files, changes in resource utilization outside of normal usage patterns, or the like. Additionally, the monitoring server may attempt to disconnect a compromised server from the network to prevent the attack from further compromising the system. The monitoring server can also activate logging hardware within the network to record network activity for further analysis. The monitoring service can continue to monitor the content server by retrieving additional security data, as illustrated at 306. Alternatively, when an anomaly is not detected, the monitoring service can, without sending an alert, retrieve additional security data from the cache servers, as illustrated at 306.

FIG. 4 shows an illustrative embodiment of a general computer system 400. The computer system 400 can include a set of instructions that can be executed to cause the computer system to perform any one or more of the methods or computer based functions disclosed herein. The computer system 400 may operate as a standalone device or may be connected, such as by using a network, to other computer systems or peripheral devices. Examples of the general computer system can include content server 204, cache server 122, client system 212, router 104, monitoring system 220, and the like.

In a networked deployment, the computer system may operate in the capacity of a server or as a client user computer in a server-client user network environment, or as a peer computer system in a peer-to-peer (or distributed) network environment. The computer system 400 can also be implemented as or incorporated into various devices, such as a personal computer (PC), a tablet PC, an STB, a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a land-line telephone, a control system, a camera, a scanner, a facsimile machine, a printer, a pager, a personal trusted device, a web appliance, a network router, switch or bridge, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. In a particular embodiment, the computer system 400 can be implemented using electronic devices that provide voice, video or data communication. Further, while a single computer system 400 is illustrated, the term “system” shall also be taken to include any collection of systems or sub-systems that individually or jointly execute a set, or multiple sets, of instructions to perform one or more computer functions.

The computer system 400 may include a processor 402, such as a central processing unit (CPU), a graphics processing unit (GPU), or both. Moreover, the computer system 400 can include a main memory 404 and a static memory 406 that can communicate with each other via a bus 408. As shown, the computer system 400 may further include a video display unit 410 such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid-state display, or a cathode ray tube (CRT). Additionally, the computer system 400 may include an input device 412 such as a keyboard, and a cursor control device 414 such as a mouse. Alternatively, input device 412 and cursor control device 414 can be combined in a touchpad or touch sensitive screen. The computer system 400 can also include a disk drive unit 416, a signal generation device 418 such as a speaker or remote control, and a network interface device 420 to communicate with a network 426. In a particular embodiment, the disk drive unit 416 may include a computer-readable medium 422 in which one or more sets of instructions 424, such as software, can be embedded. Further, the instructions 424 may embody one or more of the methods or logic as described herein. In a particular embodiment, the instructions 424 may reside completely, or at least partially, within the main memory 404, the static memory 406, and/or within the processor 402 during execution by the computer system 400. The main memory 404 and the processor 402 also may include computer-readable media.

The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of the various embodiments. The illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Additionally, the illustrations are merely representational and may not be drawn to scale. Certain proportions within the illustrations may be exaggerated, while other proportions may be minimized. Accordingly, the disclosure and the FIGs. are to be regarded as illustrative rather than restrictive.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b) and is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description of the Drawings, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments. Thus, the following claims are incorporated into the Detailed Description of the Drawings, with each claim standing on its own as defining separately claimed subject matter.

The above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments which fall within the true spirit and scope of the present disclosed subject matter. Thus, to the maximum extent allowed by law, the scope of the present disclosed subject matter is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description. 

1. A content delivery network comprising: a plurality of cache servers, each cache server configured to: receive a request for content from a client system; receive content and security data from a content server; provide the content to the client system; and provide the security data to a monitoring system remote from the client system.
 2. The content delivery network of claim 1, wherein the security data includes information from system logs, configuration information, system information, or any combination thereof.
 3. The content delivery network of claim 2, wherein the configuration information includes the size of configuration files, last modification time of the configuration files, hashes of the configuration files, recent changes to the configuration files, or any combination thereof.
 4. The content delivery network of claim 2, wherein the system information includes CPU utilization, bandwidth utilization, storage utilization, number of concurrent connections, processor temperature, fan speed, drive status, or any combination thereof.
 5. A monitoring system comprising: a processor configured to: receive security data from a cache server, the security data corresponding to a content server; analyze the security data to identify a performance anomaly; and generate an alert in response to the performance anomaly.
 6. The monitoring system of claim 5, wherein the security data includes information from system logs, configuration information, system information, or any combination thereof.
 7. The monitoring system of claim 6, wherein the configuration information includes the size of configuration files, last modification time of the configuration files, hashes of the configuration files, recent changes to the configuration files, or any combination thereof.
 8. The monitoring system of claim 6, wherein the system information includes CPU utilization, bandwidth utilization, storage utilization, number of concurrent connections, processor temperature, fan speed, drive status, or any combination thereof.
 9. The monitoring system of claim 5, wherein the processor is further configured to send an instruction to disconnect the content server from the network in response to the performance anomaly.
 10. The monitoring system of claim 5, wherein the processor is further configured to send an instruction to increase logging of network activity in response to the performance anomaly.
 11. The monitoring system of claim 5, wherein the processor is further configured to receive additional security data corresponding to the content server from a second cache server.
 12. The monitoring system of claim 11, wherein analyzing the security data to detect the performance anomaly includes comparing the security data with the additional security data to determine if the security data is altered.
 13. A computer readable medium comprising a plurality of instructions to manipulate a processor, the plurality of instructions comprising: instructions to collect security data; instructions to receive a request for content from a cache server; and instructions to provide the content and the security data to the cache server in response to the request for the content.
 14. The computer readable medium of claim 13, wherein the security data includes information from system logs, configuration information, system information, or any combination thereof.
 15. The computer readable medium of claim 14, wherein the configuration information includes the size of configuration files, last modification time of the configuration files, hashes of the configuration files, recent changes to the configuration files, or any combination thereof.
 16. The computer readable medium of claim 14, wherein the system information includes CPU utilization, bandwidth utilization, storage utilization, number of concurrent connections, processor temperature, fan speed, drive status, or any combination thereof. 